Skip to content

Release 1.2.0 — CLI peer-facts parity + enrichment/doctor fixes#4

Open
tachyon-beep wants to merge 1 commit into
mainfrom
release/1.2.0
Open

Release 1.2.0 — CLI peer-facts parity + enrichment/doctor fixes#4
tachyon-beep wants to merge 1 commit into
mainfrom
release/1.2.0

Conversation

@tachyon-beep

Copy link
Copy Markdown
Contributor

Release ceremony for 1.2.0. Diff is the two ceremony files only (_version.py + CHANGELOG.md); all code already landed on main.

Minor bump (not patch): the two new CLI subcommands are new public surface.

Included since v1.1.0

Added

  • plainweave wardline-peer-facts [--json] [--limit N] [--offset N] — CLI parity for the weft.plainweave.wardline_peer_facts.v1 envelope (previously MCP-only).
  • plainweave requirements-enrichment <entity_ref>... [--json] — CLI parity for the weft.plainweave.requirements_enrichment.v1 envelope (previously MCP-only).

Fixed

  • requirements_enrichment now drops rejected trace links before building the view — a reviewed-and-rejected binding no longer reads as requirement coverage (present); a rejected-only entity that resolves locally reads absent.
  • plainweave doctor Wardline-findings remediation is now root-aware (cd <root> && wardline scan . when the inspected root is not the cwd).

Release steps

  • Code on main
  • Version bump → 1.2.0
  • CHANGELOG [1.2.0] section + link ref
  • Merge this PR
  • Tag v1.2.0 at the merge commit

🤖 Generated with Claude Code

… fixes

Version bump + CHANGELOG ceremony for 1.2.0. The code (wardline-peer-facts
and requirements-enrichment CLI subcommands, plus the rejected-trace
enrichment-coverage fix and the root-aware Wardline doctor remediation)
already landed on main; this branch carries only the version + changelog.

Minor bump (not patch): the two new CLI subcommands are new public surface.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 02fdf2edb3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -1 +1 @@
__version__ = "1.1.0"
__version__ = "1.2.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the deployed site for 1.2.0

When this release bump is tagged as v1.2.0, the package will report 1.2.0 but the public member site remains stale: I checked site/src/pages/index.astro, which still hard-codes VERSION = '1.0.0' and a hero note saying the snapshot is 1.1.0 untagged, and .github/workflows/site.yml only deploys on site/** changes. Because this commit changes only the package version/changelog, merging it leaves users seeing contradictory release information until a separate site change is made.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant